TEIs Rel-18
R1-2302385 Rel-18 TEI proposal
on HARQ multiplexing on PUSCH Huawei, HiSilicon, Ericsson, China
Unicom
R1-2302400 RAN1 TEI proposals
for Release 18 Nokia, Nokia Shanghai Bell
R1-2302513 Rel-18 TEI proposals vivo
R1-2302576 TEI on the
introduction of a UE capability with up to 6-layer DL MIMO OPPO
R1-2302762 On PUSCH repetition
type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI ZTE, China
Telecom, Sanechips
R1-2302973 Rel-18 TEI on
pathloss RS for Type 1 CG PUSCH xiaomi
R1-2303620 Rel-18 RAN1 TEI
proposals Qualcomm Incorporated
R1-2303851 Proposals for Rel-18
TEI Ericsson, Verizon, Qualcomm
[112bis-e-R18-TEIs-01] Shinya (NTT
DOCOMO)
Email discussion on Rel-18 TEI proposals
April 26th
-
Check points: April 21,
April 26
R1-2304077 Summary #1 on
Rel-18 TEIs Moderator (NTT DOCOMO, INC.)
From April 20th GTW session,
Following proposals are considered:
TEI proposal #10: Enhancement for HARQ
multiplexing on PUSCH
o
Continue discussion to address the concern
from ZTE
TEI proposal #1: Multi-PxSCH scheduling with
single DCI
o
Continue discussion and check the view of
opponents (CATT, MediaTek)
TEI proposal #4: PUSCH repetition type A for
a PUSCH scheduled by DCI format 0_0 with CRC scrambled by C-RNTI
o
No more discussion in this meeting
TEI proposal #3: PUSCH antenna switching
o
No more discussion in this meeting
TEI proposal #10
The restriction on scheduling PDSCH after UL grant should be removed
for the case of PUSCH with repetitions
An RRC parameter to configure the function of scheduling PDSCH after
a UL DCI format and multiplexing associated HARQ on the PUSCH scheduled by the
DCI format can be introduced in Rel-18.
Note: When the restriction
on scheduling PDSCH after UL grant is released for PUSCH with repetition case, UE generates
type1/3 HARQ-ACK CB according to the existing specification.
Note: Above proposal applies to type HARQ-ACK 1/3
CB. FFS: type-2 HARQ-ACK CB
Note, the PUSCH with
repetitions can be scheduled/configured by gNB.
FFS: case
of PUSCH without repetitions
This feature is subject to UE
capability.
Companies with concerns: ZTE
TEI proposal #1
Introduce UE feature(s) for multi-PUSCH
scheduling with single DCI 0_1 for non-contiguous slots in FR1 for all defined
SCSs
Note: there is no RAN1
impact
Introduce UE feature(s) for multi-PDSCH
scheduling with single DCI 1_1 for contiguous/non-contiguous slots in FR1 for
all defined SCSs
Note: there is no RAN1
impact.
Companies with concerns: CATT, MTK
R1-2304108 Summary #2 on
Rel-18 TEIs Moderator (NTT DOCOMO, INC.)
From April 24th GTW session,
Agreement (proposal #1)
Introduce UE feature(s) for multi-PUSCH
scheduling with single DCI 0_1 for non-contiguous slots in FR1 for all defined
SCSs
Note: there is no RAN1
impact
TEI proposal #13
Rel-18 TEI proposal on pathloss RS for Type 1 CG-PUSCH is agreed. Relevant TP for clause
7.1.1 in TS 38.213 is endorsed.
|
7.1.1
UE behaviour
<Unchanged
parts are omitted>
- For a PUSCH transmission
configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant
is included in ConfiguredGrantConfig,
-
if the UE is
provided enablePL-RS-UpdateForPUSCH-SRS, the UE determines a RS resource
index  from
the value of PUSCH-PathlossReferenceRS-Id that is mapped to the sri-PUSCH-PowerControlId
indicated by the srs-ResourceIndicator value included in rrc-ConfiguredUplinkGrant
-
if the UE is not
provided enablePL-RS-UpdateForPUSCH-SRS, a RS
resource index  is
provided by a value of pathlossReferenceIndex included
in rrc-ConfiguredUplinkGrant where the RS resource
is either on serving cell  or,
if provided, on a serving cell indicated by a value of pathlossReferenceLinking
<Unchanged
parts are omitted>
|
From email decision posted on April 26th,
no consensus to endorse proposals #10 and #13.
Final summary in R1-2304223.
[113-R18-TEIs] Shinya (NTT DOCOMO)
Email discussion on Rel-18 TEIs
-
To be used for sharing updates on
online/offline schedule, details on what is to be discussed in online/offline
sessions, tdoc number of the moderator summary for online session, etc
R1-2305964 Rel-18 TEI
proposal on eCP support for NR MBS CBN, China Telecom, China Unicom, CATT,
Huawei, HiSilicon, ZTE, Sanechip (rev
of R1-2305917)
Observation 1: The specification allowing
only normal CP for 15kHz and 30kHz subcarrier spacing unnecessarily imposes the
limits to the deployments of MBS.
Observation 2: Extended CP can help improve
the special efficiency for MBS transmission.
Observation 3: The
specification impact to RAN1 is minor including, i.e., changes to TS
38.211 clause 4.2 Table 4.2-1 and clause 4.3.2 Table 4.3.2-2,
and TS 38.213 clause 11.1.1 for slot format determination.
Observation 4: RAN2 can
directly incorporate the necessary signalling for the configuration of normal
or extended CP for the CFR via a CR.
Proposal: Specify the support of
extended CP for the 15kHz and 30kHz subcarrier spacing by scaling based on eCP
for 60 kHz SCS for MBS broadcast and multicast transmission as a Rel-18 TEI.
Decision:
The document is noted.
R1-2304602 On PUSCH repetition
type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI ZTE,
China Telecom, Sanechips
R1-2304675 Rel-18 TEI proposal
on HARQ multiplexing on PUSCH Huawei, HiSilicon, Ericsson, China
Unicom
R1-2304888 Rel-18 TEI on
pathloss RS for Type 1 CG PUSCH xiaomi
R1-2305408 TEI on the
introduction of a UE capability with up to 6-layer DL MIMO OPPO
R1-2305366 Rel-18 RAN1 TEI
proposals Qualcomm Incorporated
R1-2304433 On SRS Imbalance InterDigital
To be discussed in agenda item 5.
R1-2305628 Summary #1 on
Rel-18 TEIs Moderator (NTT DOCOMO, INC.)
From Thursday session
Agreement
If UCI multiplexing of different priorities is not enabled, the restriction on scheduling PDSCH after UL grant is removed for
the case of PUSCH with repetitions except the first repetition
- UE generates Type-1 HARQ-ACK codebook
according to the existing specification with the modification of setting
the actual ACK/NACK value corresponding to PDSCH(s) scheduled after the
UL grant.
- UE generates Type-2/3 HARQ-ACK codebook
according to the existing specification.
- For Type-2 CB, UL DAI is used for
generating HARQ CB.
- This feature is subject to separate UE
capabilities for type-1, type-2, and type-3 codebooks.
- RRC parameter(s) to configure the
function of scheduling PDSCH after a UL DCI format and multiplexing
associated HARQ on a PUSCH repetition except the first repetition are
introduced in Rel-18.
- Note: the number of PUSCH repetitions can
be scheduled/configured by gNB.
- Note: same principle of current
specification which UL DAI in UL grant is applied to each PUSCH repetition
is reused.
- The timeline specified in TS 38.213
Clause 9.2.5 are satisfied, i.e.
between the last PDSCH and PUCCH, 
between the last PDCCH among UL grant /DL grant(s) and the
earliest PUCCH or PUSCH
- Additional UE capabilities are introduced
to support the following functions (UE will be configured by gNB to use
the following features via RRC)
- HARQ-ACK codebook size change on a PUCCH
slot
- PUCCH resource change on a PUCCH slot
Agreement
Rel-18 TEI proposal on pathloss RS for Type 1 CG-PUSCH is agreed.
Relevant TP for clause 7.1.1 in TS 38.213 is endorsed in principle
Note: Corresponding UE
capability and RRC configuration will be introduced and discussed in future
meetings.
|
7.1.1 UE
behaviour
<Unchanged
parts are omitted>
- For a PUSCH transmission
configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant
is included in ConfiguredGrantConfig,
-
if the UE is
provided [enablePL-RS-UpdateForType1CG-PUSCH-SRS], the UE determines a RS resource index qd from the
value of PUSCH-PathlossReferenceRS-Id that is mapped to the sri-PUSCH-PowerControlId
indicated by the srs-ResourceIndicator value included in rrc-ConfiguredUplinkGrant
-
if the UE is not
provided [enablePL-RS-UpdateForType1CG-PUSCH-SRS], a RS
resource index qd is provided by a value of pathlossReferenceIndex
included in rrc-ConfiguredUplinkGrant where
the RS resource is either on serving cell c
or, if provided, on a serving cell indicated by a value of pathlossReferenceLinking
<Unchanged
parts are omitted>
|
Final summary in R1-2306242.
From AI 5
R1-2304328 Reply LS on
1-symbol PRS RAN2, ZTE
R1-2306138 Moderator
summary for LS on 1-symbol PRS ZTE
From Thursday session
Agreement
Send the following to RAN2 in response to R1-2304328.
RAN1
would like to thank RAN2s reply R2-2304510(R1-2304328) on
1-symbol PRS.
With regard to RAN2s question, RAN1
thinks the changes to DL PRS configuration used for RTT-based Propagation Delay
Compensation are needed. In addition, RAN1 proposes the following note to be
added in the numSymbols field description:
Note: The UE does not expect to be
configured for PDC with a PRS with numSymbols equals to n1 unless an SSB
index is provided as a Type-C or Type-C & Type-D QCL source, or another PRS
resource with numSymbols more than 1 is provided as QCL source.
Furthermore, RAN1 does not expect RRM
requirements to be defined for 1-symbol PRS in PDC.
R1-2306212 Reply LS on 1-symbol PRS RAN1, ZTE
Decision:
The LS is approved.
[114-R18-TEIs] Shinya (DOCOMO)
Email discussion on Rel-18 TEIs
-
To be used for sharing
updates on online/offline schedule, details on what is to be discussed in
online/offline sessions, tdoc number of the moderator summary for online
session, etc
R1-2306882 Rel-18 TEI on complexity reduction solutions for FR2 Spreadtrum
Communications
Thursday decision: After
discussions/review with mobile operators and different vendors, proponent has
agreed that the proposed enhancements should not be further considered in this
meeting.
R1-2306988 On PUSCH repetition type A scheduled by DCI format 0-0 with
CRC scrambled by C-RNTI ZTE, China Telecom, Sanechips, NTT DOCOMO,
INC.
R1-2307518 TEI on the introduction of a UE capability with up to
6-layer DL MIMO OPPO, CMCC, China Telecom, NTT DOCOMO, Lenovo, China Unicom
R1-2307958 Rel-18 RAN1 TEI proposals Qualcomm Incorporated
R1-2308312 Summary #1 on Rel-18 TEIs Moderator (NTT DOCOMO,
INC.)
From Monday session
TEI
proposal #1: UE capability with up to 6-layer DL MIMO
o No consensus. As per
RAN1 chairs guidance, no more discussion is expected in Rel-18.
TEI
proposal #2: PUSCH repetition type A for a PUSCH scheduled by DCI format 0_0
with CRC scrambled by C-RNTI
o No consensus. As per
RAN1 chairs guidance, no more discussion is expected in Rel-18.
TEI
proposal #3: Enhanced PDCCH reception for mDCI based mTRP
o Comeback on Thursday
TEI
proposal #4: Enhancement for scheduling request
o Comeback on Thursday
TEI
proposal #5: Further complexity reductions for FR2 RedCap
o Comeback on Thursday
R1-2308485 Summary #2 on Rel-18 TEIs Moderator (NTT DOCOMO,
INC.)
From Thursday session
TEI
proposal #3:
Agreement
For multi-DCI based multi-TRP operation,
support the following:
QCL-TypeD prioritization
rules for overlapping CORESETs is performed per coresetPoolIndex value.
o
Adopt following TP in
Clause 10.1 in TS 38.213.
|
--Unchanged
part omitted------------------------
If
a UE
- is
configured for
single cell operation or for operation with carrier aggregation in a same
frequency band, and
- monitors
PDCCH candidates in overlapping PDCCH monitoring occasions in multiple
CORESETs that have been configured with same or different qcl-Type set to
'typeD' properties on active DL BWP(s) of one or more cells
the
UE monitors
PDCCHs only in a CORESET, and in any other CORESET from the multiple CORESETs
that have been configured with qcl-Type set to same
'typeD' properties as the CORESET, on the active DL BWP of a cell from the
one or more cells
- the CORESET
corresponds to the CSS
set with the lowest index in the cell with the lowest index containing CSS,
if any; otherwise, to the USS set with the lowest index in the cell with
lowest index
- the
lowest USS set index is determined over all USS sets with at least one PDCCH
candidate in overlapping PDCCH monitoring occasions
If a UE
- is
not provided coresetPoolIndex
for first CORESETs, or is provided coresetPoolIndex with value 0 for
first CORESETs, and
- is
provided coresetPoolIndex with value 1 for second CORESETs, and
- is
provided [twoQCLTypeDforMulti-DCI]
the UE applies procedures described above independently across the
first CORESETs and the second CORESETs.
--Unchanged
part omitted------------------------
|
Introduce
a UE capability for the red part of the above text.
No
consensus regarding TEI proposal #4 and #5.
From AI 5
R1-2306387 LS on longer CG-SDT periodicities RAN2, Ericsson
Decision: Discussion
on response LS to be handled in agenda item 9.15. To be moderated by Shinya
(NTT DOCOMO).
R1-2308486 Draft reply LS on longer CG-SDT periodicities Moderator
(NTT DOCOMO, INC.)
Decision
from Thursday session: The draft LS is endorsed. Final version is approved in R1-2308487.
Final summary in R1-2308553.